home *** CD-ROM | disk | FTP | other *** search
- Path: solon.com!not-for-mail
- From: The Amorphous Mass <robinson@blue.weeg.uiowa.edu>
- Newsgroups: comp.lang.c,comp.lang.c.moderated
- Subject: Re: const pointer confusion...
- Date: 26 Mar 1996 19:01:38 -0600
- Organization: University of Iowa, Iowa City, IA, USA
- Sender: clc@solutions.solon.com
- Approved: clc@solutions.solon.com
- Message-ID: <4ja41i$pgd@solutions.solon.com>
- References: <4j06gm$7oa@solutions.solon.com> <4j41hs$nku@solutions.solon.com> <4j6354$3ge@solutions.solon.com>
- NNTP-Posting-Host: solutions.solon.com
- X-Sender: robinson@red.weeg.uiowa.edu
-
- On 25 Mar 1996, Kurt Watzka wrote:
-
- >
- > The Amorphous Mass <robinson@blue.weeg.uiowa.edu> writes:
- >
- > >On 23 Mar 1996, Reed R. Mangino wrote:
- >
- > > No, p is a pointer to a constant integer. However, you are right that
- > >*p cannot change, but p can.
- >
- > >> 2) int *const p;
- > >> p is a pointer to an integer. *p can be assigned to, but p can
- > >> never be made to point to another address in memory, right?
- >
- > > This is a syntax error.
- >
- > Should I complain to my vendor? Should I complain to the vendors of
- > all compilers that accept this code?
-
- No, but you can flame me in two widely-read newsgroups for that post.
- I'll complain to the vendor of the compiler in my head.
-
- --James Robinson (robinson@cs.uiowa.edu -or- james-robinson@uiowa.edu)
- /* Indeed, C++ is a bit of an oddball of a language ... given the way that *
- * it requires private parts to be visible. This increases the strength of *
- * coupling dramatically... -- Dr. Rich Artym */
-